Methods and apparatuses for uplink transmission management

ABSTRACT

A method, performed by a User Equipment (UE), for Uplink (UL) transmission management includes the UE determining a default spatial domain transmission filter for an UL resource according to at least one Quasi Co-Location (QCL) parameter of a Control Resource Set (CORESET) after determining that the UL resource is not configured with a spatial domain transmission filter and a pathloss reference Reference Signal (RS) resource, and transmitting the UL resource by applying the default spatial domain transmission filter.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present disclosure claims the benefit of and priority to provisionalU.S. Patent Application Ser. No. 62/888,010 (“the '010 provisional”),filed on Aug. 16, 2019, entitled “Signaling Overhead Reduction for ULBeam Management.” The contents of the '010 provisional are fullyincorporated herein by reference for all purposes.

FIELD

The present disclosure generally relates to wireless communications, andmore particularly, to methods and apparatuses for Uplink (UL)transmission management.

BACKGROUND

With the tremendous growth in the number of connected devices and therapid increase in user/Network (NW) traffic volume, various efforts havebeen made to improve different aspects of wireless communication for thenext-generation wireless communication system, such as thefifth-generation (5G) New Radio (NR), by improving data rate, latency,reliability, and mobility.

The 5G NR system is designed to provide flexibility and configurabilityto optimize the NW services and types, accommodating various use casessuch as Enhanced Mobile Broadband (eMBB), Massive Machine-TypeCommunication (mMTC), and Ultra-Reliable and Low-Latency Communication(URLLC).

However, as the demand for radio access continues to increase, there isa need for further improvements of wireless communication for thenext-generation wireless communication system.

SUMMARY

The present disclosure is directed to methods and apparatuses for ULtransmission management.

According to an aspect of the present disclosure, a method, performed bya User Equipment (UE), for UL transmission management is provided. Themethod includes the UE determining a default spatial domain transmissionfilter for an UL resource according to at least one Quasi Co-Location(QCL) parameter of a Control Resource Set (CORESET) after determiningthat the UL resource is not configured with a spatial domaintransmission filter and a pathloss reference Reference Signal (RS)resource, and transmitting the UL resource by applying the defaultspatial domain transmission filter.

According to another aspect of the present disclosure, a UE for ULtransmission management in a wireless communication system is provided.The UE includes a memory and at least one processor coupled to thememory. The at least one processor is configured to determine a defaultspatial domain transmission filter for an UL resource according to atleast one QCL parameter of a CORESET after determining that the ULresource is not configured with a spatial domain transmission filter anda pathloss reference RS resource, and transmit the UL resource byapplying the default spatial domain transmission filter.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingdetailed description when read with the accompanying figures. Variousfeatures are not drawn to scale. Dimensions of various features may bearbitrarily increased or reduced for clarity of discussion.

FIG. 1 illustrates a list of spatial relation information configured forPhysical UL Control Channel (PUCCH) operations, in accordance with animplementation of the present disclosure.

FIG. 2 illustrates multiple Sounding Reference Signal (SRS) resourcesets each configured with a pathloss reference RS resource, inaccordance with an implementation of the present disclosure.

FIG. 3 illustrates a flowchart for a method of UL transmissionmanagement, in accordance with an implementation of the presentdisclosure.

FIG. 4 illustrates a flowchart for a method of UL transmissionmanagement, in accordance with an implementation of the presentdisclosure.

FIG. 5 illustrates a flowchart for a method of UL transmissionmanagement, in accordance with an implementation of the presentdisclosure.

FIG. 6 illustrates a block diagram of a node for wireless communication,in accordance with various aspects of the present disclosure.

DESCRIPTION

The following description contains specific information pertaining toexemplary implementations in the present disclosure. The drawings in thepresent disclosure and their accompanying detailed description aredirected to merely exemplary implementations. However, the presentdisclosure is not limited to merely these exemplary implementations.Other variations and implementations of the present disclosure willoccur to those skilled in the art. Unless noted otherwise, like orcorresponding elements among the figures may be indicated by like orcorresponding reference numerals. Moreover, the drawings andillustrations in the present disclosure are generally not to scale, andare not intended to correspond to actual relative dimensions.

The following description contains specific information pertaining toexample implementations in the present disclosure. The drawings in thepresent disclosure and their accompanying detailed description aredirected to merely example implementations. However, the presentdisclosure is not limited to merely these example implementations. Othervariations and implementations of the present disclosure will occur tothose skilled in the art. Unless noted otherwise, like or correspondingelements among the figures may be indicated by like or correspondingreference numerals. Moreover, the drawings and illustrations in thepresent disclosure are generally not to scale, and are not intended tocorrespond to actual relative dimensions.

For consistency and ease of understanding, like features are identified(although, in some examples, not illustrated) by numerals in the examplefigures. However, the features in different implementations may differin other respects, and thus shall not be narrowly confined to what isillustrated in the figures.

References to “one implementation,” “an implementation,” “exampleimplementation,” “various implementations,” “some implementations,”“implementations of the present disclosure,” etc., may indicate that theimplementation(s) of the present disclosure so described may include aparticular feature, structure, or characteristic, but not every possibleimplementation of the present disclosure necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one implementation,” “in an example implementation,”or “an implementation,” do not necessarily refer to the sameimplementation, although they may. Moreover, any use of phrases like“implementations” in connection with “the present disclosure” are nevermeant to characterize that all implementations of the present disclosuremust include the particular feature, structure, or characteristic, andshould instead be understood to mean “at least some implementations ofthe present disclosure” includes the stated particular feature,structure, or characteristic. The term “coupled” is defined asconnected, whether directly or indirectly through interveningcomponents, and is not necessarily limited to physical connections. Theterm “comprising,” when utilized, means “including, but not necessarilylimited to”; it specifically indicates open-ended inclusion ormembership in the so-described combination, group, series, and theequivalent.

The term “and/or” herein is only an association relationship fordescribing associated objects, and represents that three relationshipsmay exist, for example, A and/or B may represent that: A exists alone, Aand B exist at the same time, and B exists alone. “A and/or B and/or C”may represent that at least one of A, B and C exists. In addition, thecharacter “/” used herein generally represents that the former andlatter associated objects are in an “or” relationship.

Additionally, for the purpose of non-limiting explanation, specificdetails, such as functional entities, techniques, protocols, standards,and the like, are set forth for providing an understanding of thedescribed technology. In other examples, a detailed description ofwell-known methods, technologies, systems, architectures, and the likeare omitted so as not to obscure the description with unnecessarydetails.

Persons skilled in the art will immediately recognize that any NWfunction(s) or algorithm(s) described in the present disclosure may beimplemented by hardware, software, or a combination of software andhardware. Described functions may correspond to modules that may besoftware, hardware, firmware, or any combination thereof. The softwareimplementation may comprise computer-executable instructions stored oncomputer-readable media such as memory or other types of storagedevices. For example, one or more microprocessors or general-purposecomputers with communication processing capability may be programmedwith corresponding executable instructions and carry out the describedNW function(s) or algorithm(s). The microprocessors or general-purposecomputers may be formed of Applications Specific Integrated Circuitry(ASIC), programmable logic arrays, and/or using one or more DigitalSignal Processor (DSPs). Although some of the example implementationsdescribed in this specification are oriented to software installed andexecuting on computer hardware, nevertheless, alternative exampleimplementations implemented as firmware or as hardware or combination ofhardware and software are well within the scope of the presentdisclosure.

The computer-readable medium includes but is not limited to RandomAccess Memory (RAM), Read-Only Memory (ROM), Erasable ProgrammableRead-Only Memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM), flash memory, Compact Disc Read-Only Memory (CD-ROM),magnetic cassettes, magnetic tape, magnetic disk storage, or any otherequivalent medium capable of storing computer-readable instructions.

A radio communication NW architecture (e.g., a Long Term Evolution (LTE)system, an LTE-Advanced (LTE-A) system, or an LTE-Advanced Pro system)typically includes at least one Base Station (BS), at least one UE, andone or more optional NW elements that provide connection towards an NW.The UE communicates with the NW (e.g., a Core NW (CN), an Evolved PacketCore (EPC) NW, an Evolved Universal Terrestrial Radio Access NW(E-UTRAN), a Next-Generation Core (NGC), or an Internet), through aRadio Access NW (RAN) established by the BS.

It should be noted that, in the present disclosure, a UE may include,but is not limited to, a mobile station, a mobile terminal or device, auser communication radio terminal. For example, a UE may be a portableradio equipment, which includes, but is not limited to, a mobile phone,a tablet, a wearable device, a sensor, or a Personal Digital Assistant(PDA) with wireless communication capability. The UE is configured toreceive and transmit signals over an air interface to one or more cellsin a RAN.

A BS may include, but not limited to, a Node B (NB) as in the UniversalMobile Telecommunication System (UMTS), an evolved Node B (eNB) as inthe LTE-A, a Radio NW Controller (RNC) as in the UMTS, a Base StationController (BSC) as in the Global System for Mobile communications(GSM)/GSM EDGE Radio Access NW (GERAN), a Next Generation eNB (ng-eNB)as in an E-UTRA BS in connection with the 5GC, a next-generation Node B(gNB) as in the 5G Access NW (5G-AN), and any other apparatus capable ofcontrolling radio communication and managing radio resources within acell. The BS may connect to serve the one or more UEs through a radiointerface to the NW.

A BS may be configured to provide communication services according to atleast one of the following Radio Access Technologies (RATs): WorldwideInteroperability for Microwave Access (WiMAX), GSM (often referred to as2G), GERAN, General Packet Radio Service (GPRS), UMTS (often referred toas 3G) based on basic Wideband-Code Division Multiple Access (W-CDMA),High-Speed Packet Access (HSPA), LTE, LTE-A, enhanced LTE (eLTE), NR(often referred to as 5G), and LTE-A Pro. However, the scope of thepresent disclosure should not be limited to the protocols mentionedabove.

The BS may be operable to provide radio coverage to a specificgeographical area using a plurality of cells included in the RAN. The BSmay support the operations of the cells. Each cell is operable toprovide services to at least one UE within its radio coverage. Morespecifically, each cell (often referred to as a serving cell) mayprovide services to serve one or more UEs within its radio coverage,(e.g., each cell schedules the Downlink (DL) and optionally UL resourcesto at least one UE within its radio coverage for DL and optionally ULpacket transmissions). The BS may communicate with one or more UEs inthe radio communication system through the plurality of cells. A cellmay allocate sidelink (SL) resources for supporting proximity service(ProSe). Each cell may have overlapped coverage areas with other cells.In Multi-RAT Dual Connectivity (MR-DC) cases, the primary cell of aMaster Cell Group (MCG) or a Secondary Cell Group (SCG) may be called asa Special Cell (SpCell). A Primary Cell (PCell) may refer to the SpCellof an MCG. A PSCell may refer to the SpCell of an SCG. MCG refers to agroup of serving cells associated with the Master Node (MN), comprisingthe SpCell and optionally one or more secondary cells (SCells). SCGrefers to a group of serving cells associated with the Secondary Node(SN), comprising of the SpCell and optionally one or more SCells.

As discussed above, the frame structure for NR is to support flexibleconfigurations for accommodating various next generation (e.g., 5G)communication requirements, such as eMBB, mMTC, and URLLC, whilefulfilling high reliability, high data rate, and low latencyrequirements. The orthogonal frequency-division multiplexing (OFDM)technology, as agreed in the 3^(rd) Generation Partnership Project(3GPP), may serve as a baseline for an NR waveform. The scalable OFDMnumerology, such as the adaptive sub-carrier spacing, the channelbandwidth, and the cyclic prefix (CP), may also be used. Additionally,two coding schemes are considered for NR: (1) low-density parity-check(LDPC) code and (2) polar code. The coding scheme adaption may beconfigured based on the channel conditions and/or service applications.

Moreover, it is also considered that in a transmission time interval ofa single NR frame, at least DL transmission data, a guard period, and ULtransmission data should be included, where the respective portions ofthe DL transmission data, the guard period, the UL transmission datashould also be configurable, for example, based on the NW dynamics ofNR. In addition, SL resources may also be provided in an NR frame tosupport ProSe services.

The NR system may support beam management for enabling, but not limitedto, high-frequency band (e.g., millimeter-wave frequency band)communication. To combat higher pathloss in a high-frequency band, abeamforming technique is adopted for providing additional gain, with thecost of reduced spatial coverage for signal transmission and reception.To make up for the lost spatial coverage of beamforming, a beam issteered towards different directions in Time Division Multiplexing (TDM)manner so that after a certain period of time, the UE or the gNB canstill learn its environment with a desired spatial coverage.

In NR, for example, Release-15 (Rel-15), beam management is supported bya Transmission Configuration Indication (TCI) framework and spatialrelation information for DL and UL, respectively. For DL, differenttypes of a Qusai-CoLocation (QCL) assumption is indicated. Among them,QCL-type D is related to spatial receiving characteristics that may beused by a UE for receiving a target RS or channel. In the UL direction,the spatial transmitting characteristic may be indicated to the UE viathe spatial relation information provided by the NW side. A UE mayperform UL transmission for UL channel(s) and signal(s) accordingly.

For a UE with beam correspondence, DL beam management procedures thatmay involve DL beam measurement and reporting may provide enoughinformation for selecting a suitable UL beam for UL transmission. Inthis case, not only the UL beam sweeping procedure can be saved, butalso the UL beam indication signaling. However, such an UL operationmode is not yet introduced in the NR system.

To save UL beam indication signaling for, e.g., an UL control channel(e.g., PUCCH), an UL data channel (e.g., Physical UL Shared Channel(PUSCH)), or an UL SRS, enabling default spatial relation informationfor the concerned UL channel(s)/signal(s) for a beam correspondent UEbased on the DL QCL assumption may be needed. In NR Rel-15 (e.g.,Technical Specification (TS)38.214 V15.5.0), a QCL assumption for theDemodulation RS (DM-RS) ports of a Physical DL Shared Channel (PDSCH) ofa serving cell may be determined based on the QCL parameters of theCORESET(s) configured to a UE. More specifically, the QCL assumption ofthe DM-RS ports of a PDSCH of a serving cell may be determined based onthe following text in Table 1:

TABLE 1 If a DL scheduling offset of scheduling DL Control Information(DCI) is larger than a threshold (timeDurationForQCL) If TCI indicationfield is not provided in the scheduling DCI QCL assumption for the PDSCHis identical to the QCL assumption whichever is applied for the CORESETused for the transmission of Physical DL Control Channel (PDCCH)corresponding to the scheduling DCI. If TCI indication field is providedin the scheduling DCI QCL assumption for the PDSCH is determined basedon the TCI field in the scheduling DCI. If the DL scheduling offset ofthe scheduling DCI is less or equal to a threshold (timeDurationForQCL)The UE may assume that QCL parameters of PDSCH of the serving cell areidentical to the QCL parameter(s) used for the PDCCH QCL indication ofthe CORESET associated with a monitored search space with the lowestCORESET identifier (CORESET-ID) in the latest slot in which one or moreCORESETs within the active Bandwidth Part (BWP) of the serving cell aremonitored by the UE.

However, in order to enable the spatial relation information of a PUCCHand/or the spatial relation information of an SRS to follow QCLparameters of a CORESET, at least one of the following dimensions (i) to(vi) may also be considered:

-   -   (i) PUCCH resources may be grouped, and the default spatial        relation information determination for PUCCH may be PUCCH        resource group-based.    -   (ii) DL CORESETs may be grouped, with a CORESET group        corresponding to, e.g., the same Transmit-Receive Point (TRP).        The default spatial relation information determination for a        PUCCH/SRS may correspond to different CORESET groups.    -   (iii) SRS resource set configured with usage: {codebook,        nonCodebook, antennaSwitching} may need to be differentiated.    -   (iv) Pathloss reference RS for UL power control may be        configured in different manners for PUCCH resources and for SRS        resources. Default spatial relation information determination        may take this part into account.    -   (v) Periodic(P)/semi-persistent (SP)/aperiodic (AP) PUCCH        transmissions may follow different behavior for determining        default spatial relation information.    -   (vi) Default spatial relation information determination may        differentiate itself between self-carrier scheduling and        cross-carrier scheduling.

It should be understood that a spatial relation may be conceptualized asa spatial domain transmission filter or a beam. Thus, in the presentdisclosure, the terms “spatial relation,” “spatial domain transmissionfilter,” and “beam” may be utilized interchangeably.

1. Default Spatial Relation for PUCCH

For PUCCH operations, a UE may be configured with at least one spatialrelation (or “spatial domain transmission filter”) via Radio ResourceControl (RRC) signaling (e.g., an RRC configuration) from a BS. Eachspatial domain transmission filter may be indicated by a correspondingspatial relation information parameter (e.g., an Information Element(IE) denoted as pucch-spatialRelationlnfo) in the RRC configuration. Inaddition, the spatial relation information parameter may also indicate aDL pathloss reference RS for estimating DL pathloss for UL PUCCH powercontrol purposes. For example, the spatial relation informationparameter may include (or may be associated with) an IE denoted aspucch-PathlossReferenceRS

For each PUCCH resource, its corresponding spatial domain transmissionfilter may be selected from the spatial domain transmission filter(s)configured to the UE, and activated via Medium Access Control(MAC)-Control Element (CE) activation signaling from the BS.

FIG. 1 illustrates a list of spatial relation information configured forPUCCH operations, in accordance with an implementation of the presentdisclosure.

As illustrated in FIG. 1, a UE may be configured with a list 108 ofspatial relation information via RRC signaling from a BS. The list 108of spatial relation information may include one or morepucch-spatialRelationlnfo IEs (e.g., pucch-spatialRelationlnfo #1 topucch-spatialRelationInfo #N, where N is a natural number), where eachpucch-spatialRelationlnfo IE may be used to indicate or determine aspatial domain transmission filter or a beam for PUCCH operations. Forexample, for transmission of a PUCCH resource, the UE may select one ofthe pucch-spatialRelationlnfo IEs in the list 108 to apply (e.g., basedon the MAC-CE activation signaling from a BS). As illustrated in FIG. 1,the UE may be instructed by the BS (e.g., via the MAC-CE activationsignaling) to use/apply the spatial domain transmission filter indicatedby the pucch-spatialRelationlnfo IE #1 to transmit the PUCCH resource102, and use/apply the spatial domain transmission filter indicated bythe pucch-spatialRelationlnfo IE #3 to transmit the PUCCH resource 104and the PUCCH resource 106.

In addition, each pucch-spatialRelationlnfo IE in the list of spatialrelation information may indicate a corresponding (DL) pathlossreference RS resource (not illustrated). For example, eachpucch-spatialRelationlnfo IE in the list of spatial relation informationmay include (or be associated with) an indication of a pathlossreference RS resource.

If the UE is configured with only one spatial domain transmission filter(e.g., there is only one pucch-spatialRelationlnfo IE in the list 108),the present spatial domain transmission filter in the list (e.g., thelist 108) may be used for the transmissions of the PUCCH resources(e.g., PUCCH resources 102, 104 and 106) allocated to the UE without theMAC-CE activation signaling.

In one implementation, the PUCCH resource may be used in a P/SP/APmanner. For example, a P/SP PUCCH resource may be used for P/SP ChannelState Information (CSI) reporting, and an AP PUCCH resource may be usedfor Hybrid Automatic Repeat reQuest (HARQ)-Acknowledgement (ACK)feedback transmission(s).

An AP PUCCH transmission may be triggered by DCI from a BS. The DCI maybe transmitted by the BS in a DL Component Carrier (CC) paired with anUL CC where the AP PUCCH transmission takes place (self-carrierscheduling), or in a DL CC not paired with the UL CC where the AP PUCCHtransmission takes place (cross-carrier scheduling). Supplementary UL(SUL) operations may be considered as self-carrier scheduling in thiscase.

In one implementation, a UE may determine a spatial domain transmissionfilter for a PUCCH resource without explicit signaling from a BS. Forexample, a UE may apply a default spatial domain transmission filter fora PUCCH resource when the UE cannot acquire thepucch-SpatialRelationInfo IE from NW signaling (e.g., signaling from theBS).

In one implementation, the default spatial domain transmission filter(s)for individual PUCCH resources allocated to a UE may be determinedindependently.

In one implementation, the PUCCH resources may be grouped as one or morePUCCH resource groups. In this case, the default spatial domaintransmission filter may be determined for each PUCCH resource groupindependently.

In one implementation, the grouping of the PUCCH resources may be formedimplicitly or explicitly based on NW signaling. For example, the PUCCHresources associated with different UE panels may correspond todifferent PUCCH resource groups.

In one implementation, a single default spatial domain transmissionfilter may be used for transmissions of all PUCCH resources allocated tothe UE.

In one implementation, the default spatial domain transmission filterfor a PUCCH resource may follow the QCL parameter(s) of a CORESET, wherethe CORESET may be used for DL PDCCH monitoring.

In one implementation, the CORESET may be associated with a CORESETgroup.

In one implementation, the CORESET group may be associated with a TRP.

In one implementation, the CORESET may or may not correspond to a DL CCthat is paired with the UL CC where the PUCCH resource resides. Forexample, the transmission on the PUCCH resource may be triggered by DCI,where a carrier indication field in the DCI may identify the UL CC.

In one implementation, a PUCCH resource may be associated with theCORESET by a BS via implicit/explicit signaling. For example, the PUCCHresource may be associated with (or included in) a PUCCH resource group.The BS may associate the PUCCH resource group with a CORESET group(including the CORESET) by mapping the PUCCH resource group to theCORESET group via NW signaling.

In one implementation, the CORESET may be associated with a monitoredsearch space with the lowest CORESET-ID in the latest slot in which theassociated CORESET group (including the CORESET) is monitored by the UE.

In one implementation, the associated CORESET group may include allconfigured CORESETs in the active BWP of a serving cell (or a CC).

In one implementation, the transmission on the PUCCH resource maycorrespond to an instance of a P/SP PUCCH transmission.

In one implementation, the CORESET may be associated with a search spaceon which the DCI that triggers the transmission on the PUCCH resource isreceived by the UE. For example, the transmission on the PUCCH resourcetransmission may correspond to an AP PUCCH transmission.

In one implementation, the CORESET may be preconfigured/predetermined.In one example, the CORESET is predetermined as having a highest orlowest CORESET-ID index in the active DL BWP in the CC.

In one implementation, the RS associated with the QCL-type D in the QCLparameters of the CORESET may be used to determine the default spatialdomain transmission filter. In one implementation, the RS may be apathloss reference RS. For example, when the spatial domain transmissionfilter for PUCCH transmission is not provided by NW signaling viapucch-SpatialRelationInfo, the pathloss reference RS for UL powercontrol of the PUCCH transmission may be determined as:

the RS indicated by the QCL parameter(s) of the CORESET (if there aremultiple RSs indicated by the QCL parameters, the RS associated with theQCL-type D may be selected); or

-   -   a preconfigured RS.

In one implementation, for determining a default spatial domaintransmission filter for the transmission on a PUCCH resource (or a“PUCCH transmission”) when the corresponding pucch-SpatialRelationlnfoof the PUCCH resource is not provided by the NW signaling, the PUCCHresource may be associated with (or included in) a PUCCH resource group,where the PUCCH resource group may be associated with a CORESET group.In this case, the default spatial domain transmission filter for thetransmission on the PUCCH resource may be determined based on the QCLparameter(s) of the CORESET associated with a monitored search spacewith the lowest CORESET-ID in the latest slot in which the CORESET groupis monitored by the UE, if the PUCCH resource is for a P/SPtransmission. In one implementation, the default spatial domaintransmission filter for the transmission on the PUCCH resource may bedetermined based on the QCL parameter(s) of the CORESET associated witha search space on which the DCI that triggers the transmission on thePUCCH resource is received, if the PUCCH resource is for an APtransmission.

In one implementation, if there is more than one RS associated with theQCL parameter(s), the RS associated with the QCL-type D may be used todetermine the default spatial domain transmission filter for a PUCCHresource. In one example, for power control of the transmission on thePUCCH resource, the pathloss reference RS may be used as the defaultspatial domain transmission filter.

2. Default Spatial Relation for SRS

The usage of an SRS resource set may be configured as one of{beamManagement, codebook, nonCodebook, antennaSwitching} as specifiedin the 3GPP NR specification, e.g., TS 38.331 V15.5.0. Each SRS resourcemay be RRC-configured by a BS with an SRS-SpatialRelationInfo IE fordetermining its spatial domain transmission filter for the ULtransmission. For each SRS resource set, a (DL) pathloss reference RSresource (e.g., indicated by an IE denoted as pathlossReferenceRS) maybe provided for estimating the DL pathloss for UL SRS power controlpurposes.

FIG. 2 illustrates multiple SRS resource sets each configured with a(DL) pathloss reference RS resource, in accordance with animplementation of the present disclosure.

As illustrated in FIG. 2, a UE may be provided (or configured) withseveral SRS resource sets (e.g., including an SRS resource set 210 andan SRS resource set 220). Each SRS resource set may be associated with(or include) one or more SRS resources. For example, the SRS resourceset 210 may include M SRS resources (e.g., the SRS resource #1 212, theSRS resource #2 214, and the SRS resource #2 216), and the SRS resourceset 220 may include K SRS resources (e.g., the SRS resource #1 224, theSRS resource #2 226, and the SRS resource #2 228), where M and K arenatural numbers. Each SRS resource in an SRS resource set may beconfigured with a spatial domain transmission filter (e.g., indicated bythe SRS-SpatialRelationlnfo IE). For example, if the correspondingSRS-SpatialRelationlnfo IE is provided, an SRS resource may betransmitted based on a spatial domain transmission filter indicated bythe corresponding SRS-SpatialRelationInfo IE.

In addition, each SRS resource set may be configured with a pathlossreference RS resource (e.g., indicated by the pathlossReferenceRS IE).As illustrated in FIG. 2, the SRS resource set 210 may be configuredwith the pathloss reference RS resource #1 218, and the SRS resource set220 may be configured with the pathloss reference RS resource #2 222.

An SRS resource may be used in a P/SP/AP manner. For example, an AP SRStransmission may be triggered by DCI, where the DCI may be transmitted1) in a DL CC paired with an UL CC where the AP SRS transmission takesplace, or 2) in a DL CC not paired with the UL CC where the AP PUCCHtransmission takes place. In this case, SUL operation(s) may beconsidered as scenario 1) described above, for example.

In the following subsections, methods for determining a default spatialdomain transmission filter for transmission(s) on an SRS resource areprovided. For ease of illustration, an SRS resource with the usage ofits associated SRS resource set being configured as “codebook” may bereferred to as an “SRS-codebook resource,” an SRS resource with theusage of its associated SRS resource set being configured as“nonCodebook” may be referred to as an “SRS-nonCodebook resource,” andan SRS resource with the usage of its associated SRS resource set beingconfigured as “antennaSwitching” may be referred to as an“SRS-antennaSwitching resource.” For example, if the usage of the SRSresource set 210 illustrated in FIG. 2 is configured as “nonCodebook,”the SRS resources 212, 214, and 216 associated with (or included in) theSRS resource set 210 are SRS-nonCodebook resources.

2.1 SRS-nonCodebook Resource

In one implementation, there may be 1, 2, 3, or 4 SRS-nonCodebookresources being configured in a corresponding resource set. In addition,there may be an associatedCSl-RS IE being configured in anSRS-nonCodebook resource set. In this case, the spatial domaintransmission filter for an SRS-nonCodebook resource may be determinedbased on explicit NW signaling via the associatedCSl-RS IE or theSRS-SpatialRelationlnfo IE, but the NW may not provide both to the UE atthe same time.

In one implementation, the spatial domain transmission filter for anSRS-nonCodebook resource may be determined without NW explicitsignaling. For example, a default spatial domain transmission filter maybe applied by a UE when, for example, neither the associatedCSl-RS IEnor the SRS-SpatialRelationlnfo IE can be acquired from the NWsignaling.

In one implementation, the default spatial domain transmission filter(s)for individual SRS-nonCodebook resources allocated to a UE may bedetermined independently.

In one implementation, the SRS-nonCodebook resources allocated to the UEmay be grouped as one or more SRS-nonCodebook resource sets (e.g., theSRS resource sets 210 and 220 illustrated in FIG. 2). In this case, adefault spatial domain transmission filter may be determined for anSRS-nonCodebook resource set. For example, an SRS-nonCodebook resourceset may correspond to a UE panel, and multiple SRS-nonCodebook resourcesets may be configured for mapping to multiple UE panels.

In one implementation, the default spatial domain transmission filterfor an SRS-nonCodebook resource may follow the QCL parameter(s) of aCORESET, where the CORESET is for DL PDCCH monitoring.

In one implementation, the CORESET may be associated with a CORESETgroup.

In one implementation, the CORESET group may be associated with a TRP.

In one implementation, the CORESET may or may not correspond to a DL CCthat is paired with the UL CC where the SRS-nonCodebook resourceresides. For example, the transmission on the SRS-nonCodebook resourcemay be triggered by DCI, where a carrier indication field in the DCI mayidentify the UL CC.

In one implementation, the SRS-nonCodebook resource may be associatedwith the CORESET by the NW via implicit/explicit signaling. For example,the SRS-nonCodebook resource set associated with (or including) theSRS-nonCodebook resource may map to a CORESET group associated with (orincluding) the CORESET by NW signaling.

In one implementation, the CORESET may be associated with a monitoredsearch space with the lowest CORESET-ID in the latest slot in which theassociated CORESET group (e.g., including the CORESET) are monitored bythe UE.

In one implementation, the associated CORESET group may include allconfigured CORESETs in the DL active BWP of a serving cell (or a CC).

In one implementation, the transmission on the SRS-nonCodebook resourcemay correspond to an instance of P/SP SRS transmission.

In one implementation, the CORESET may be associated with a search spaceon which the DCI that triggers the transmission on the SRS-nonCodebookresource is received by the UE. For example, the transmission on theSRS-nonCodebook resource transmission may correspond to an AP SRStransmission.

In one implementation, the CORESET may be preconfigured/predetermined.In one example, the CORESET may be predetermined/preconfigured as theone with the highest or the lowest CORESET-ID in the active DL BWP inthe CC.

In one implementation, the default spatial domain transmission filtermay follow the QCL parameter(s) of the PathlossReferenceRS IE configuredfor the associated SRS-nonCodebook resource set, if the UE is providedwith the PathlossReferenceRS IE.

In one implementation, the RS associated with the QCL-type D in the QCLparameter(s) of the CORESET may be used to determine the default spatialdomain transmission filter.

In one implementation, the default spatial domain transmission filter ofan SRS-nonCodebook resource may follow the spatial domain transmissionfilter (e.g., indicated by the pucch-SpatialRelationlnfo IE) of a PUCCHresource with the lowest PUCCH resource ID (e.g., PUCCH-ResourceId)within the active UL BWP of the serving cell that the SRS-nonCodebookresource resides. The PUCCH resource with the lowest PUCCH-ResourceIdmay be selected from the PUCCH resources whose spatial relationinformation has been activated by MAC-CE signaling.

In one implementation, when the PathlossReferenceRS IE is not providedby NW signaling for the associated SRS-nonCodebook resource set (e.g.,in a case that the SRS resource set 210 illustrated in FIG. 2 is notconfigured with the pathloss reference RS resource #1 218), the pathlossreference RS for UL power control of the SRS-nonCodebook resourcetransmission may be determined as:

the RS indicated by the QCL parameter(s) of the CORESET (if there aremultiple RSs indicated by the QCL parameters, the RS associated with theQCL-type D may be selected);

a CSI-RS (e.g., indicated by the associatedCSl-RS IE) associated withthe corresponding SRS-nonCodebook resource set; or

a preconfigured RS.

In one implementation, for determining a default spatial domaintransmission filter for the transmission on an SRS-nonCodebook resourcewhen the SRS-SpatialRelationlnfo IE corresponding to the SRS-nonCodebookand the associatedCSl-RS IE corresponding to the SRS-nonCodebook are notprovided by the NW signaling, the SRS-nonCodebook resource set includingthe SRS-nonCodebook resource may be associated with a CORESET group. Inthis case, the default spatial domain transmission filter for thetransmission on the SRS-nonCodebook resource may be determined based onthe QCL parameter(s) of the CORESET associated with a monitored searchspace with the lowest CORESET-ID in the latest slot in which the CORESETgroup are monitored by the UE, if the SRS-nonCodebook resource is for aP/SP transmission. In one implementation, if the SRS-nonCodebookresource is for an AP transmission, the default spatial domaintransmission filter for the transmission on the SRS-nonCodebook resourcemay be determined based on the QCL parameter(s) of the CORESETassociated with a search space on which the DCI that triggers thetransmission on the SRS-nonCodebook resource is received.

In one implementation, if there is more than one RS associated with theQCL parameter(s), the RS associated with the QCL-type D may be appliedfor determining the default spatial domain transmission filter.

In one implementation, for power control of the transmission on anSRS-nonCodebook resource, when a UE is not configured with a pathlossreference RS for the corresponding SRS-nonCodebook resource set (e.g.,in a case that the UE is not configured with the PathlossReferenceRS IEfor the corresponding SRS-nonCodebook resource set), a pathlossreference RS may be determined as the default spatial domaintransmission filter for the corresponding SRS-nonCodebook resource.

2.2 SRS-Codebook Resource(s) and SRS-AntennaSwitching Resource(s)

In one implementation, there may be 1 or 2 SRS-codebook resources beingconfigured in a corresponding resource set. A UE may determine a spatialdomain transmission filter for an SRS-codebook resource and for anSRS-antennaSwitching resource without being explicitly indicated by theNW. In addition, a default spatial domain transmission filter may beapplied when, for example, the UE cannot acquire theSRS-SpatialRelationlnfo IE from the NW signaling. In the following, forease of illustration, an SRS resource that is either an SRS-codebookresource or an SRS-antennaSwitching resource may be denoted as an“SRS-ac resource.”

In one implementation, the default spatial domain transmission filter(s)for individual SRS-ac resources allocated to a UE may be determinedindependently.

In one implementation, the default spatial domain transmission filtermay be configured by the BS based on an SRS-ac resource set basis.

In one implementation, if only a subset of SRS-ac resources in an SRS-acresource set is not configured with the SRS-SpatialRelationlnfo IE, thedefault spatial domain transmission filter may be applicable to thesubset of SRS-ac resources.

In one implementation, the methods for determining default spatialdomain transmission filter(s) may only be applicable when each SRS-acresource in an SRS-ac resource set is not configured with anSRS-SpatialRelationlnfo IE.

In one implementation, an SRS-ac resource set may be associated with aUE panel.

In one implementation, the default spatial domain transmission filter ofan SRS-ac resource may follow the QCL parameter(s) of a CORESET for DLPDCCH monitoring.

In one implementation, the CORESET may be associated with a CORESETgroup.

In one implementation, the CORESET group may be associated with a TRP.

In one implementation, the CORESET may or may not correspond to a DL CCthat is paired with the UL CC where the SRS-ac resource resides. Forexample, the transmission on the SRS-ac resource may be triggered byDCI, where a carrier indication field in the DCI may identify the UL CC.

In one implementation, an SRS-ac resource may be associated with theCORESET by NW via implicit or explicit signaling. For example, theSRS-ac resource set associated with (or including) the SRS-ac resourcemay map to a CORESET group associated with (or including) the CORESET byNW signaling.

In one implementation, the CORESET may be associated with a monitoredsearch space with the lowest CORESET-ID in the latest slot in which anassociated CORESET group (including the CORESET) is monitored by the UE.

In one implementation, the associated CORESET group may include allconfigured CORESETs in the DL active BWP of a serving cell (or a CC).

In one implementation, the transmission on the SRS-ac resource maycorrespond to an instance of a P/SP SRS transmission.

In one implementation, the CORESET may be associated with a search spaceon which the DCI that triggers the transmission on the SRS-ac resourceis received.

In one implementation, the transmission on the SRS-ac resourcetransmission may correspond to an AP SRS transmission.

In one implementation, the CORESET may be preconfigured/predetermined.In one example, the CORESET is predetermined as the one with a higher orlowest CORESET-ID index in the active DL BWP in the CC.

In one implementation, the default spatial domain transmission filterfor an SRS-ac resource may follow the QCL parameter(s) of thePathlossReferenceRS IE of the associated SRS-nonCodebook resource set(including the SRS-ac resource), if the UE is configured with thePathlossReferenceRS IE.

In one implementation, the RS associated with the QCL-type D in the QCLparameter(s) may be used as a default spatial domain transmission filterfor an SRS-ac resource.

In one implementation, the default spatial domain transmission filter ofan SRS-ac resource may follow the spatial domain transmission filter(e.g., determined by the pucch-SpatialRelationInfo IE) of the PUCCHresource with the lowest PUCCH-Resourceld within the active UL BWP ofthe serving cell where the SRS -ac resource resides.

In one implementation, when the PathlossReferenceRS IE is not providedby NW signaling for the associated SRS-ac resource set, a pathlossreference RS for UL power control for the SRS-ac resource transmissionmay be determined as:

the RS indicated by the QCL parameters of the CORESET (if there aremultiple RSs indicated by the QCL parameters, the RS associated withQCL-type D may be selected); or

a preconfigured RS.

In one implementation, for determining a default spatial domaintransmission filter for the transmission on an SRS-ac resource when theSRS-SpatialRelationlnfo IE corresponding to the SRS-ac resource is notprovided by the NW signaling, the SRS-ac resource set(including theSRS-ac resource) may be associated with a CORESET group. In this case,the default spatial domain transmission filter for the transmission onthe SRS-ac resource may be determined based on the QCL parameter(s) ofthe CORESET associated with a monitored search space with the lowestCORESET-ID in the latest slot in which the CORESET group is monitored bythe UE, if the SRS-nonCodebook resource is for a P/SP transmission. Inone implementation, the default spatial domain transmission filter forthe transmission on the SRS-nonCodebook resource may be determined basedon the QCL parameter(s) of the CORESET associated with a search space onwhich the DCI that triggers the transmission on the SRS-ac resource isreceived, if the SRS-ac resource is for an AP transmission.

In one implementation, if there is more than one RS associated with theQCL parameter(s), the RS associated with the QCL-type D may be appliedfor determining the default spatial domain transmission filter.

In one implementation, for power control of the transmission on theSRS-ac resource when the PathlossReferenceRS IE is not configured forthe corresponding SRS-ac resource set, a pathloss reference RS may beused as the default spatial domain transmission filter for the SRS-acresource.

FIG. 3 illustrates a flowchart for a method 300 of UL transmissionmanagement, in accordance with an implementation of the presentdisclosure. As illustrated in FIG. 3, the method 300 includes action 302and 304.

In action 302, a UE may determine a default spatial domain transmissionfilter for an UL resource according to at least one QCL parameter of aCORESET after determining that the UL resource is not configured with aspatial domain transmission filter and a pathloss reference RS resource.

Two antenna ports are said to be QCL if properties of the channel overwhich a symbol on one antenna port is conveyed can be inferred from thechannel over which a symbol on the other antenna port is conveyed. The“properties of the channel” above may include Doppler shift, Dopplerspread, average delay, delay spread, and spatial Reception (Rx)parameters. These properties may be categorized into different QCLtypes/parameters (e.g., QCL-TypeA parameter(s), QCL-TypeB parameter(s),QCL-TypeC parameter(s), and QCL-TypeD parameter(s)) in NRspecifications. For example, the QCL-TypeD (parameter) may refer to aspatial receiving parameter. The QCL-TypeD (parameter) may also bereferred to a beam. The UE may determine the default spatial domaintransmission filter based on the QCL type(s)/parameter(s) of theCORESET.

In one implementation, the UL resource may be an SRS resource includedin an SRS resource set that is not configured with the pathlossreference RS resource. As illustrated in FIG. 2, the BS may configurethe pathloss reference RS resource based on an SRS resource set basis,where each SRS resource set may include one or more SRS resources. Inthis case, the UE may apply the various implementations described inSection 2.0 to determine whether the UL resource is configured with aspatial domain transmission filter and a pathloss reference RS resource.For example, when an SRS resource set is not configured with aPathlossReferenceRS IE (indicating a pathloss reference RS resource) bythe BS, the UE may determine that the SRS resource set is not configuredwith a pathloss reference RS. Also, the UE may determine that the SRSresource is not configured with a spatial domain transmission filterwhen the SRS resource is not configured with an SRS-SpatialRelationlnfoIE (or a spatial relation information parameter) indicating a spatialdomain transmission filter for SRS transmission.

In one implementation, the UL resource and the CORESET may be associatedwith the same CC. For example, in a case that the CORESET is associatedwith (or included in) a CORESET group in a DL active BWP of a CC, andalso the UL resource is provided in the UL counterpart of the CC (eitherpair CC or unpair CC), the UL resource and the CORESET may be consideredto be associated with the same CC.

In one implementation, the UL resource may be a PUCCH resource. In thiscase, the UE may apply the various implementations described in Section1 to determine whether the UL resource is configured with a spatialdomain transmission filter and a pathloss reference RS resource. Forexample, when a PUCCH resource is not configured with apucch-spatialRelationInfo IE or apucch-PathlossReferenceRS IE, the UEmay determine that the PUCCH resource is not configured with a pathlossreference RS resource. Also, the UE may determine that a PUCCH resourceis not configured with a spatial domain transmission filter when thePUCCH resource is not configured with the pucch-spatialRelationlnfo IE(or a spatial relation information parameter) indicating a spatialdomain transmission filter for PUCCH transmission.

In one implementation, the UE may determine a default pathloss referenceRS resource for the UL resource by selecting an RS resource withQCL-type D from a plurality of RS resources indicated by the at leastone QCL parameter of the CORESET. For example, if the QCL parameter(s)of the CORESET indicates an RS #1 and an RS #2, where the RS #1 isassociated with QCL-type A and the RS #2 is associated with QCL-type D,the UE may select the RS #2 as the default pathloss reference RSresource for the UL resource.

In action 304, the UE may transmit the UL resource by applying thedefault spatial domain transmission (Tx) filter. For example, the UE maytransmit the UL resource by using the spatial Tx and/or Rx parameter(s)corresponding to the default spatial domain transmission filter.

FIG. 4 illustrates a flowchart for a method 400 of UL transmissionmanagement, in accordance with an implementation of the presentdisclosure. The method 400 may be performed by a UE independently or incombination with various implementation(s) described in the presentdisclosure. In addition, it should be noted that although actions 402,404, and 406 are delineated as separate actions represented asindependent blocks in FIG. 4, these separately delineated actions shouldnot be construed as necessarily order dependent. The order in which theactions are performed in FIG. 4 is not intended to be construed as alimitation, and any number of the described blocks may be combined inany order to implement the method or an alternate method. For example,the order of action 404 and action 406 may be exchanged.

In action 402, a UE may receive a configuration (e.g., an RRCconfiguration) via RRC signaling.

In action 404, the UE may determine that an SRS resource set that is notconfigured with a pathloss reference RS resource is used for anon-codebook-based PUSCH transmission according to the configuration.For example, the UE may determine that the usage of the SRS resource setis configured as “nonCodebook” according to the configuration.

In action 406, the UE may determine that an SRS resource included in theSRS resource set is not associated with a CSI-RS resource according tothe configuration. For example, the UE may determine that the SRSresource is not associated with a CSI-RS resource when noassociatedCSl-RS IE (for indicating a CSI-RS resource) is configured forthe SRS resource set. The SRS resource may be an example of the ULresource mentioned in FIG. 3.

FIG. 5 illustrates a flowchart for a method 500 of UL transmissionmanagement, in accordance with an implementation of the presentdisclosure. The method 500 may be performed by a UE independently or incombination with various implementation(s) described in the presentdisclosure.

In action 502, a UE may receive a configuration (e.g., an RRCconfiguration) via RRC signaling.

In action 504, the UE may determine whether a spatial domaintransmission filter set including at least one candidate spatial domaintransmission filter for PUCCH transmissions is provided in theconfiguration. As illustrated in FIG. 1, the list 108 of spatialrelation information may indicate a spatial domain transmission filterset including N candidate spatial domain transmission filters (e.g.,indicated by pucch-spatialRelationlnfo #1 to pucch-spatialRelationlnfo#N, respectively). The spatial domain transmission filter for a PUCCHresource may be selected from one of N candidate spatial domaintransmission filters (e.g., via MAC CE signaling from the BS).

In action 506, the UE may determine that a PUCCH resource is notconfigured with a spatial domain transmission filter when the spatialdomain transmission filter set is not provided in the configuration. Forexample, if the PUCCH resource is not RRC-configured with a list ofspatial relation information (e.g., the list 108 of spatial relationinformation illustrated in FIG. 1), the UE may determine that the PUCCHresource is not configured with a spatial domain transmission filter.The PUCCH resource may be an example of the UL resource mentioned inFIG. 3.

In one implementation, the UE may transmit, to a BS, a UE capabilitymessage indicating that beam correspondence is supported by the UE. Ifthe UE supports beam correspondence, it may mean that the UE has theability to, for example, select a suitable beam for UL transmissionbased on DL measurements with or without relying on UL beam sweeping.

The following provides non-limiting descriptions of certain terms.

Beam Failure Recovery: movements in the environment or other events, maylead to a currently established beam pair being rapidly blocked withoutsufficient time for the regular beam adjust to adapt based on the beamreporting mechanism (the beam reporting mechanism may be similar to theCSI reporting mechanism taken place in the Physical (PHY) channels). Abeam failure recovery procedure may be used to deal with suchoccurrences with a short reaction time.

Beam: the term “beam” here may be replaced by “spatial domaintransmission filter.” For example, when a UE reports a preferred gNB Txbeam, the UE is essentially selecting a spatial filter used by the gNB.The term “beam information” may be used to provide information aboutwhich beam/spatial domain transmission filter is being used/selected. Inone implementation, individual RSs may be transmitted by applyingindividual beams (spatial domain transmission filters). Thus, the term“beam” or “beam information” may be represented by RS resource index(es)in some implementations of the present disclosure.

HARQ: A functionality ensures delivery between peer entities at Layer 1(e.g., the PHY Layer). A single HARQ process may support one TransportBlock (TB) when the PHY layer is not configured for DL/UL spatialmultiplexing, and when the PHY layer is configured for DL/UL spatialmultiplexing, a single HARQ process may support one or multiple TBs. Inone implementation, there may be one HARQ entity per serving cell. EachHARQ entity may support a parallel (number) of DL and UL HARQ processes.

Timer: A MAC entity may setup one or more timers for individualpurposes, for example, triggering some UL signaling retransmissions orlimiting some UL signaling retransmission periods. A timer is runningonce it is started, until it is stopped or until it expires; otherwiseit is not running. A timer can be started if it is not running orrestarted if it is running. A timer is always started or restarted fromits initial value. The initial value may be but not limited to beconfigured by a BS (e.g., gNB) via DL RRC signaling.

BWP: A subset of the total cell bandwidth of a cell is referred to as aBWP. Bandwidth adaptation may be achieved by configuring a UE withBWP(s) and telling the UE which of the configured BWPs is currently theactive one. To enable Bandwidth Adaptation (BA) on the PCell, a gNB mayconfigure the UE with UL and DL BWP(s). To enable BA on SCells in caseof Carrier Aggregation (CA), the gNB may configure the UE with DL BWP(s)at least (e.g., there may be none in the UL). For the PCell, the initialBWP may be the BWP used for initial access. For the SCell(s), theinitial BWP may be the BWP configured for the UE to first operate atSCell activation. A UE may be configured with a first active UL BWP by afirstActiveUplinkBWP IE. If the first active UL BWP is configured for anSpCell, the firstActiveUplinkBWP IE field may contain the ID of the ULBWP to be activated upon the UE performing the RRC (re-)configurationprocess. If the field is absent, the RRC (re-)configuration process maynot impose a BWP switch. If the first active UL BWP is configured for anSCell, the firstActiveUplinkBWP IE field may contain the ID of the ULBWP to be used upon MAC-activation of an SCell.

QCL: Two antenna ports are quasi co-located if properties of the channelover which a symbol on one antenna port is conveyed can be inferred fromthe channel over which a symbol on the other antenna port is conveyed.The “properties of the channel” described above may include at least oneof Doppler shift, Doppler spread, average delay, delay spread, andspatial Rx parameters. These properties may be categorized intodifferent QCL types in NR TSs. For example, the QCL-type D refers to aspatial Rx parameter. The QCL-type D may be referred to as a “beam.”

TCI state: a TCI state may contain parameters for configuring a QCLrelationship between one or two DL RSs and a target RS set. For example,a target RS set may be the DM-RS ports of a PDSCH or a PDCCH.

Normal Scheduling Request (SR): A normal SR may be used for requestingan UL Shared Channel (UL-SCH) resource (e.g., a PUSCH resource) for newtransmission. The UE may be configured with zero, one, or more than onenormal SR configuration. A normal SR configuration may include a set ofPUCCH resources for SR across different BWPs and cells. For a logicalchannel, at most one PUCCH resource for SR may be configured per BWP.Each normal SR configuration may correspond to one or more logicalchannels. Each logical channel may be mapped to zero or one normal SRconfiguration. The normal SR configuration of the logical channel thattriggered a Buffer Status Report (BSR) procedure (if the configurationof the BSR procedure exists) may be considered as the correspondingnormal SR configuration for the triggered SR procedure. When a normal SRprocedure is triggered, the normal SR procedure may be considered aspending until it is canceled.

Beam Correspondence: beam correspondence is the ability of a UE toselect a suitable beam for UL transmission based on DL measurements withor without relying on UL beam sweeping. Alternatively, beamcorrespondence may be referred to as the ability of a UE to be indicateda suitable beam for DL reception based on the UL beam sweepingprocedure.

FIG. 6 illustrates a block diagram of a node 600 for wirelesscommunication, in accordance with various aspects of the presentdisclosure. As illustrated in FIG. 6, the node 600 may include atransceiver 606, a processor 608, a memory 602, one or more presentationcomponents 604, and at least one antenna 610. The node 600 may alsoinclude a Radio Frequency (RF) spectrum band module, a BS communicationsmodule, an NW communications module, and a system communicationsmanagement module, Input/Output (I/O) ports, I/O components, and powersupply (not explicitly illustrated in FIG. 6). Each of these componentsmay be in communication with each other, directly or indirectly, overone or more buses 624. In one implementation, the node 600 may be a UEor a BS that performs various functions described herein, for example,with reference to FIGS. 1 through 5.

The transceiver 606 having a transmitter 616 (e.g.,transmitting/transmission circuitry) and a receiver 618 (e.g.,receiving/reception circuitry) may be configured to transmit and/orreceive time and/or frequency resource partitioning information. In oneimplementation, the transceiver 606 may be configured to transmit indifferent types of subframes and slots, including, but not limited to,usable, non-usable and flexibly usable subframes and slot formats. Thetransceiver 606 may be configured to receive data and control channels.

The node 600 may include a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the node 600 and include both volatile (and non-volatile) media andremovable (and non-removable) media. By way of example, and notlimitation, computer-readable media may include computer storage mediaand communication media. Computer storage media may include bothvolatile (and non-volatile) and removable (and non-removable) mediaimplemented according to any method or technology for storage ofinformation such as computer-readable.

Computer storage media includes RAM, ROM, EEPROM, flash memory (or othermemory technology), CD-ROM, Digital Versatile Disks (DVD) (or otheroptical disk storage), magnetic cassettes, magnetic tape, magnetic diskstorage (or other magnetic storage devices), etc. Computer storage mediadoes not include a propagated data signal. Communication media maytypically embody computer-readable instructions, data structures,program modules, or other data in a modulated data signal such as acarrier wave or other transport mechanism and include any informationdelivery media. The term “modulated data signal” may mean a signal thathas one or more of its characteristics set or changed in such a manneras to encode information in the signal. By way of example, and notlimitation, communication media may include wired media such as a wiredNW or direct-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer-readable media.

The memory 602 may include computer-storage media in the form ofvolatile and/or non-volatile memory. The memory 602 may be removable,non-removable, or a combination thereof. For example, the memory 602 mayinclude solid-state memory, hard drives, optical-disc drives, etc. Asillustrated in FIG. 6, the memory 602 may store computer-readableand/or—executable instructions 614 (e.g., software codes) that areconfigured to, when executed, cause the processor 608 to perform variousfunctions described herein, for example, with reference to FIGS. 1through 5. Alternatively, the instructions 614 may not be directlyexecutable by the processor 608 but may be configured to cause the node600 (e.g., when compiled and executed) to perform various functionsdescribed herein.

The processor 608 (e.g., having processing circuitry) may include anintelligent hardware device, a Central Processing Unit (CPU), amicrocontroller, an ASIC, etc. The processor 608 may include memory. Theprocessor 608 may process the data 612 and the instructions 614 receivedfrom the memory 602, and information through the transceiver 606, thebaseband communications module, and/or the NW communications module. Theprocessor 608 may also process information to be sent to the transceiver606 for transmission through the antenna 610, to the NW communicationsmodule for transmission to a CN.

One or more presentation components 604 may present data indications toa person or other device. Examples of presentation components 604 mayinclude a display device, speaker, printing component, vibratingcomponent, etc.

From the above description, it is manifested that various techniques maybe used for implementing the concepts described in the presentapplication without departing from the scope of those concepts.Moreover, while the concepts have been described with specific referenceto certain implementations, a person of ordinary skill in the art wouldrecognize that changes may be made in form and detail without departingfrom the scope of those concepts. As such, the described implementationsare to be considered in all respects as illustrative and notrestrictive. It should also be understood that the present applicationis not limited to the particular implementations described above. Still,many rearrangements, modifications, and substitutions are possiblewithout departing from the scope of the present disclosure.

What is claimed is:
 1. A method performed by a User Equipment (UE) forUplink (UL) transmission management in a wireless communication system,the method comprising: determining a default spatial domain transmissionfilter for an UL resource according to at least one Quasi Co-Location(QCL) parameter of a Control Resource Set (CORESET) after determiningthat the UL resource is not configured with a spatial domaintransmission filter and a pathloss reference Reference Signal (RS)resource; and transmitting the UL resource by applying the defaultspatial domain transmission filter.
 2. The method of claim 1, whereinthe UL resource is a Sounding Reference Signal (SRS) resource includedin an SRS resource set that is not configured with the pathlossreference RS resource.
 3. The method of claim 2, further comprising:receiving a configuration via Radio Resource Control (RRC) signaling;determining that the SRS resource set is used for a non-codebook-basedPhysical Uplink Shared Channel (PUSCH) transmission according to theconfiguration; and determining that the UL resource is not associatedwith a Channel State Information Reference Signal (CSI-RS) resourceaccording to the configuration.
 4. The method of claim 2, wherein the ULresource and the CORESET are associated with a same Component Carrier(CC).
 5. The method of claim 1, wherein the UL resource is a PhysicalUplink Control Channel (PUCCH) resource.
 6. The method of claim 5,further comprising: receiving a configuration via Radio Resource Control(RRC) signaling; determining whether a spatial domain transmissionfilter set including at least one candidate spatial domain transmissionfilter for PUCCH transmissions is provided in the configuration; anddetermining that the UL resource is not configured with the spatialdomain transmission filter when the spatial domain transmission filterset is not provided in the configuration.
 7. The method of claim 5,further comprising: transmitting, to a Base Station (BS), a UEcapability message indicating that beam correspondence is supported bythe UE.
 8. The method of claim 1, further comprising: determining adefault pathloss reference RS resource for the UL resource by selectingan RS resource with a QCL-type D from a plurality of RS resourcesindicated by the at least one QCL parameter of the CORESET.
 9. A UserEquipment (UE) for Uplink (UL) transmission management in a wirelesscommunication system, the UE comprising: a memory; and at least oneprocessor coupled to the memory, the at least one processor beingconfigured to: determine a default spatial domain transmission filterfor an UL resource according to at least one Quasi Co-Location (QCL)parameter of a Control Resource Set (CORESET) after determining that theUL resource is not configured with a spatial domain transmission filterand a pathloss reference Reference Signal (RS) resource; and transmitthe UL resource by applying the default spatial domain transmissionfilter.
 10. The UE of claim 9, wherein the UL resource is a SoundingReference Signal (SRS) resource included in an SRS resource set that isnot configured with the pathloss reference RS resource.
 11. The UE ofclaim 10, wherein the at least one processor is further configured to:receive a configuration via Radio Resource Control (RRC) signaling;determine that the SRS resource set is used for a non-codebook-basedPhysical Uplink Shared Channel (PUSCH) transmission according to theconfiguration; and determine that the UL resource is not associated witha Channel State Information Reference Signal (CSI-RS) resource accordingto the configuration.
 12. The UE of claim 10, wherein the UL resourceand the CORESET are associated with a same Component Carrier (CC). 13.The UE of claim 9, wherein the UL resource is a Physical Uplink ControlChannel (PUCCH) resource.
 14. The UE of claim 13, wherein the at leastone processor is further configured to: receive a configuration viaRadio Resource Control (RRC) signaling; determine whether a spatialdomain transmission filter set including at least one candidate spatialdomain transmission filter for PUCCH transmissions is provided in theconfiguration; and determine that the UL resource is not configured withthe spatial domain transmission filter when the spatial domaintransmission filter set is not provided in the configuration.
 15. The UEof claim 13, wherein the at least one processor is further configuredto: transmit, to a Base Station (BS), a UE capability message indicatingthat beam correspondence is supported by the UE.
 16. The UE of claim 9,wherein the at least one processor is further configured to: determine adefault pathloss reference RS resource for the UL resource by selectingan RS resource with a QCL-type D from a plurality of RS resourcesindicated by the at least one QCL parameter of the CORESET.